An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

I just tried to renew my APP, and it confirmed via email that it is renewed. But, also says that it needs to be reviewed. Seems like alot of people are having this issue. I have a pilot study on Monday which requires users to use the app, so I placed an expedited review request, and the system is saying I don't have an APP in the review stage. App is no longer on the App Store. Please advise!

Hi everyone — looking for guidance from developers who’ve dealt with App Review + subscriptions. We’ve submitted our iOS app for review and have been rejected 3 times related to subscriptions / in-app purchase rules. Here’s our setup: We offer a Premium subscription that unlocks extra features in the app. We do NOT allow users to purchase/subscribe inside the iOS app. There is no IAP, no checkout, and no purchase flow in the app. Users can only subscribe outside the app (on our website). If a user already has a Premium account (subscribed on the website), they can log in on iOS and use all Premium features inside the app. To us, this appears similar to what apps like Spotify do: from the iOS app you can’t subscribe to Premium via IAP; they direct users to the website, and once subscribed externally, Premium works inside the app. We’ve shared this context with the review team, but we still haven’t gotten a clear explanation of what specifically is not allowed in our case. My questions to the community: Is this model acceptable under App Store guidelines (no in-app purchase, subscription only on the web, and premium features unlocked after login)? If it is acceptable, what is the recommended way to present this to App Review so the app gets approved? (e.g., specific wording, metadata notes, review notes, removing certain UI, etc.) If it’s not acceptable, what’s the correct approach Apple expects for a Premium subscription that unlocks digital features? Has anyone had a similar rejection and successfully resolved it — what changes or steps worked? Any advice on how to get this approved would be hugely appreciated. See below the example from Spotify app on IOS.

I am trying to resubmit my app after failing a few times (first time doing this). Anyhow, when resubmitting the last 2 times, the "In-App Purchases and Subscriptions" section was always present on the version page so I could choose my IAP's and Subscriptions before submitting for review. Currently, I am trying to resubmit again, and the "In-App Purchases and Subscriptions" section is nowhere to be found and no matter what I try to do, it's just not showing up. Currently, all my IAP's and Subscriptions have a "Waiting for Review" status and my app status is "1.0 Prepare for Submission". Any ideas how I can get around this???

I am in the middle of trying to get an app approved for beta release and the back and forth with the App Store reviewers has been incredibly frustrating and concerning. On Tuesday, I created an app record for my app but quickly realized I made it under the wrong account- I'm working for a company that has a few brands under it's umbrella, and I was under the wrong account when I created the app record. Rather than wait several days to get Apple's approval to transfer app ownership, I decided to delete that app record and create a new one under the proper account. Worst mistake of my life. Now, Apple is insisting that the new app record is spam despite my clarification that I own the other app record and that it was deleted before the new one was created. I have no choice but to believe that somebody else is using our branding and asset somewhere in the App Store that I can't see. Does anybody know how I can resolve this? It should have never taken me the whole week to make an app available on test flight and my stakeholders are not pleased, and I have no clear path towards resolution that will allow me to use the proper branding with the proper company account. App review refuse to offer any solutions, I am stuck with a brand name that I can't use because it's associated with an app I already deleted.

Title: Stuck in a loop between Guideline 2.1 and 2.2: Reviewer refuses to play for 5 minutes. Body: I am an independent developer struggling with a repetitive rejection cycle for over a month. I need advice on how to handle a clear contradiction in the review process. The Loop: Initial Rejection (2.1): Reviewer said they couldn't locate the IAP. My Action: I added a prominent "IAP Test" button on the title screen to skip gameplay. Second Rejection (2.2): A different reviewer said the "IAP Test" button is a "Beta feature" and not appropriate for production. My Action: I removed the button and implemented a "Secret Command" (Easter Egg) that enables an "Assist Mode" (extending the timer to 5 minutes) so the reviewer can easily clear the game and reach the IAP screen in about 5-6 minutes. Latest Rejection (2.1): The reviewer now says: "While we appreciate you provide an instruction... we require a quicker way to access in-app purchases without spending significant time to play games." The Current Solution: In my next submission, I am implementing a "Direct Warp" feature. Tapping the title logo 7 times will trigger a secret transition directly to the Ending Scene (IAP screen). The Contradiction & Question: Apple forbids "Test Buttons" (2.2), but now they refuse to spend even 3-5 minutes of gameplay to reach the IAP. I am forced to implement a "Warp" feature just to satisfy the reviewer's convenience. Has anyone else experienced a reviewer refusing to perform 5-6 minutes of gameplay? Is a "Secret Warp" considered a "Beta feature" under 2.2, or is it an acceptable compromise for 2.1? I want to ensure I don't get rejected for 2.2 again.

Hello everyone, does anyone know why the reply to app review button is gone? The reviewer says reply to this message, but I don't have the reply button as I used to. Is this a bug?

We submitted a build on the 26th, but it stayed in “Waiting for Review” until January 3rd. Thinking something was wrong, we withdrew it and resubmitted, but after 5 days it’s still pending. We have an important campaign in January and this delay is seriously affecting us. We also emailed support but haven’t received any reply. How can we resolve this?

Hi, I'm constatly receiving the same answer of Apple Review about my subscriptions. Guideline 3.1.2 - Business - Payments - Subscriptions We noticed that your app did not meet all the terms and conditions for auto-renewing subscriptions, as specified in Schedule 2, section 3.8(b) of the Paid Applications agreement. – A functional link to the privacy policy We were unable to find the following required item(s) in your app's metadata: – A functional link to the Terms of Use (EULA) Next Steps To resolve this issue, please add this missing information. If the above information is present, please reply to this message in App Store Connect to provide details on where to locate it. If you are using the standard Apple Terms of Use (EULA), you will need to include a link to the Terms of Use in your App Description. If you are using a custom EULA, add it in App Store Connect. Resources Learn more about offering auto-renewable subscriptions on the App Store. Review the Paid Applications agreement. I provided all the information in the paywall, the privacy policy link in app information, and EULA link in the App Description. Also I contacted apple several times and I didn't receive any answer. This is so disgusting and I should be able to realese the app by next week. If anyone can help me please contact me.

Hi there, I dont now what to do anymore and you help is more than appreciated. My app + subscriptions has been certified before 8 days on Monday, 8th but my subscriptions are not shown in the App Store. That leads to a loading spinner since 8 days in my production app! I have an email, where I see that the app + all 6 subscriptions has been approved. On the other hand I see that my subscriptions are still in review and dont see them below the app in the App Store. I was given last week on Tuesday (before 7 days) an expedite review for the subscriptions, because the Apple developer support was writing that the subscriptions are not yet certified. The expedite review has not taken place since 7 days or its not true what the Apple Developer Support is writing (subscriptions need to be reviewed). I think the subscriptions are not linked to the app and I am in a dead lock situation. I need your help, because I have fears that I receive 1 star recommendations and the developer support cannot help me since 8 days. Best regards Tino Link to the App: https://apps.apple.com/de/app/vario-one/id1605797423

I understand how frustrating ASO can be when progress feels slow. To grow beyond keyword optimization, it helps to learn from indie developer resources, communities, and guides that focus on practical app marketing strategies and visibility.

Should you rely only on organic installs, or would a mix of strategies work better? Isn’t optimizing keywords and refining creatives essential for higher visibility? Would running Apple Search Ads not further amplify reach? And doesn’t encouraging strong reviews ultimately help in improving both ranking and credibility?

App Store Optimization in 2026 requires a more strategic, data driven approach as Apple’s algorithms evolve and user expectations continue to rise. This overview covers the key ASO trends iOS developers should focus on, including AI powered keyword insights, product page optimization, conversion focused testing, and advanced localization to drive sustainable organic growth.

User spending on mobile apps keeps rising, but competition is growing faster, making App Store Optimization a critical pillar of mobile growth by improving visibility, reducing cost per install, and driving stronger organic performance. This post highlights the most important ASO trends for 2026, including AI driven optimization, user intent focus, localization, creative testing, analytics, and privacy first strategies to help apps grow consistently on the App Store.

I am seeking guidance after experiencing what appears to be an inconsistent and unresponsive review process. My app was rejected under Guideline 4.3(b) (Spam - saturated category) and Guideline 2.1 (App Completeness - IAP not found in binary). I would like to highlight several concerns: Regarding 2.1 - IAP Issue: The rejection states that In-App Purchase products "could not be found in the submitted binary." However, a previous reviewer successfully accessed and screenshotted the exact purchase screen in an earlier review cycle. The IAP is clearly implemented and functional. This inconsistency suggests the current reviewer may not have thoroughly tested the app. Regarding 4.3(b) - Spam: I have submitted detailed appeal notes explaining the unique, differentiating features of my app that are not found in any competing applications in this category. These include: Integration with real-time external data sources (not static content) Cultural and regional elements unique to my market AI-powered contextual features beyond template-based functionality A distinctive companion feature focused on reflective dialogue rather than predictions Despite providing this documentation, I receive identical templated rejection responses with no acknowledgment of the specific points raised in my appeals. My Questions: How can I ensure that reviewers actually read and consider the detailed notes provided in appeals? If a previous reviewer could access the IAP screen, why would the current reviewer claim it doesn't exist? Apple actively features apps in this category in editorial collections. What specific criteria differentiates "approved" apps from those rejected as spam? I have invested significant development time and resources into creating something genuinely innovative, not a clone. I respectfully request that my submission receive a thorough, hands-on evaluation rather than a surface-level category-based rejection. Any guidance from Apple staff or developers who have navigated similar situations would be greatly appreciated. Most Importantly: This experience is deeply discouraging and exhausting. This process does not feel developmental or constructive that it feels like a barrier designed to wear down independent developers. The inconsistency between platforms is striking: my app was approved on Google Play without any issues, and we were expecting simultaneous production releases. Instead, I am trapped in a rejection loop here while my competitor advantage erodes daily. How can it be that one platform recognizes the legitimacy of my work while the other dismisses it with templated responses? Simply providing vague assurances and surface-level category rejections helps no one, not developers, not users, not the ecosystem. Independent developers are the backbone of app marketplace diversity. When the review process becomes this opaque and unresponsive, it doesn't protect quality that it stifles innovation and consolidates the market in favor of established players who can afford to wait indefinitely. I am not asking for special treatment. I am asking for a fair, thorough, and consistent review.

Hi, Our app submission is being rejected many times. We have provided the required adjustments but still receiving the following: Guideline 3.1.2 - Business - Payments - Subscriptions Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The app's binary is missing the following required information: A functional link to the Terms of Use (EULA) A functional link to the privacy policy Next Steps Update the app binary to include the information specified above. Resources Apps offering auto-renewable subscriptions must include all of the following required information in the binary: Title of auto-renewing subscription (this may be the same as the in-app purchase product name) Length of subscription Price of subscription, and price per unit if appropriate Functional links to the privacy policy and Terms of Use (EULA) The app metadata must also include functional links to the privacy policy in the Privacy Policy field in App Store Connect and the Terms of Use (EULA) in the App Description or EULA field in App Store Connect. Pls help, thank you.

Hello App Review Team, My app has been in review since December 12 (TestFlight), and I wanted to kindly ask if there is any additional information, clarification, or action required from my side to proceed with the review. App ID: com.prestige.Listie Name of app: Listie Shop & Share Please let me know if anything is missing or if I can assist in any way to help complete the review process. Thank you very much for your time and support. Best regards, Filip

App is approved and on App Store but Subscription is in review and localizations rejected. no way to edit. anyone here that go this flow resolved and how?

Hi, anyone has any updates on the recent App Store Review delays?

Hello, I have a problem regarding my App review. The issue: "Guideline 3.1.2 - Business - Payments - Subscriptions Issue Description The submission did not include all the required information for apps offering auto-renewable subscriptions. The app's metadata is missing the following required information: A functional link to the Terms of Use (EULA). If you are using the standard Apple Terms of Use (EULA), include a link to the Terms of Use in the App Description. If you are using a custom EULA, add it in App Store Connect." My explanation: I'm using Apple's original EULA in my app. The EULA was already in the "About" section. It redirects to the EULA page on Apple's official website. However, since my app also has a payment screen, I added the same information below the payment screen and submitted it for review again. Unfortunately, it's still being rejected for the same reason. I've requested a full, detailed explanation via email, but they keep sending me the same copy-and-paste message. I want to resolve this issue as soon as possible, so I decided to ask you here. Please check the screenshots and let me know what's the problem. Best regards, DryreL

Hello Apple Developer Community and App Review Team, Please help! Our app is "In Review" status for 4 days on a resubmission. We have requested an expedited review on 30 December because we had a launch with 20k users. My Apple ID: 6745441830 SKU: panduoapp This delay has pushed our planned launch back by over a week, impacting more than 20,000 pre-registered users who are waiting to access the app's core features (AI interactions, community, etc.). My developer had never seen this before and he got a new app submitted yesterday and got approved within 3 hours. Is this level of "In Review" time common right now during the post-holiday period? We've seen quick reviews on other similar apps recently, so wondering if this might be stuck or require a nudge. Any advice on next steps (beyond Resolution Center inquiry) or similar experiences? We've double-checked build attachment, IAP config, paywall links, and reviewer notes (including demo access). Thank you!